Wireless communication system, apparatus for suppporting data flow and methods therefor

ABSTRACT

An apparatus for use in allocating resource in a wireless communication system employing transfer communication protocol (TCP) based data transfer between a network and a wireless subscriber communication unit comprises a scheduler located in the network, wherein the scheduler buffers a TCP data segment for downlink (DL) transmission. A transmitter is arranged to transmit the buffered TCP data segment to the UE; wherein the message indicates an allocation of DL resources plus sufficient uplink resources to transfer a stand-alone ACK data segment. In this manner, for example in large bulk data transfer cases, a reduced latency may be achieved that may lead to improved throughput, due to the fact that the overall throughput may be limited by the window size (i.e. number of unacknowledged segments) rather than the throughput possible across the air interface.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a U.S. application claiming priority from UnitedKingdom Application No. GB0616241.6 filed Aug. 16, 2006, which is hereinincorporated by reference in its entirety.

FIELD OF THE INVENTION

This invention relates to a mechanism to support Internet Protocol dataflows within a wireless communication system. The invention isapplicable to, but not limited to, packet data transmissions, forexample, for use in the universal mobile telecommunication standard.

BACKGROUND OF THE INVENTION

In a cellular communication system, a geographical region is dividedinto a number of cells, each of which is served by base stations,sometimes referred to as Node-Bs. The base stations are interconnectedby a fixed network that is able to transfer data between respective basestations. A mobile station, sometimes referred to as user equipment(UE), is served via a radio communication link from the base station ofthe cell within which the mobile station is situated.

A typical cellular communication system extends coverage over an entirecountry and comprises hundreds or even thousands of cells supportingthousands or even millions of mobile stations. Communication from amobile station to a base station is known as the uplink (UL), andcommunication from a base station to a mobile station is known as thedownlink (DL).

The fixed network interconnecting the base stations is operable to routedata between any two base stations, The fixed network interconnectingthe base stations is operable to route data between any two basestations, thereby enabling a mobile station in a cell to communicatewith a mobile station in any other cell. In addition, the fixed networkcomprises gateway functions for interconnecting to external networkssuch as the Internet or the Public Switched Telephone Network (PSTN),thereby allowing mobile stations to communicate with landline telephonesand other communication terminals connected by a landline. Furthermore,the fixed network comprises much of the functionality required formanaging a conventional cellular communication network includingfunctionality for routing data, admission control, resource allocation,subscriber billing, mobile station authentication etc.

Currently, the most ubiquitous cellular communication system is the 2ndgeneration communication system known as the Global System for Mobilecommunication (GSM). GSM uses a technology known as Time DivisionMultiple Access (TDMA) wherein user separation is achieved by dividingfrequency carriers into 8 discrete time slots, which individually can beallocated to a user. Further description of the GSM TDMA communicationsystem can be found in ‘The GSM System for Mobile Communications’ byMichel Mouly and Marie Bernadette Pautet, Bay Foreign Language Books,1992, ISBN 2950719007.

Currently, 3rd generation systems are being rolled out to furtherenhance the communication services provided to mobile users. The mostwidely adopted 3rd generation communication systems are based on CodeDivision Multiple Access (CDMA) technology. Both Frequency DivisionDuplex (FDD) and Time Division Duplex (TDD) techniques employ this CDMAtechnology. In CDMA systems, user separation is obtained by allocatingdifferent spreading and scrambling codes to different users on the samecarrier frequency and in the same time intervals. In TDD, additionaluser separation is achieved by assigning different time slots todifferent users similarly to TDMA. However, in contrast to TDMA, TDDprovides for the same carrier frequency to be used for both uplink anddownlink transmissions. An example of a communication system using thisprinciple is the Universal Mobile Telecommunication System (UMTS).Further description of CDMA and specifically of the Wideband CDMA(WCDMA) mode of UMTS can be found in ‘WCDMA for UMTS’, Harri Holma(editor), Antti Toskala (Editor), Wiley & Sons, 2001, ISBN 0471486876.

In a 3rd generation cellular communication system, the communicationnetwork comprises a core network and a Radio Access Network (RAN). Thecore network is operable to route data from one part of the RAN toanother, as well as interfacing with other communication systems. Inaddition, it performs many of the operation and management functions ofa cellular communication system, such as billing. The RAN is operable tosupport wireless user equipment over a radio link of the air interface.The RAN comprises the base stations, which in UMTS are known as Node Bs,as well as Radio Network Controllers (RNC) that control the basestations and the communication over the air interface.

The RNC performs many of the control functions related to the airinterface including radio resource management and routing of data to andfrom appropriate base stations. It further provides the interfacebetween the RAN and the core network. An RNC and associated basestations are known as a Radio Network Subsystem (RNS).

3rd generation cellular communication systems have been specified toprovide a large number of different services including efficient packetdata services. For example, downlink packet data services are supportedwithin the 3GPP release 5 specifications in the form of the High SpeedDownlink Packet Access (HSDPA) service. A High Speed Uplink PacketAccess (HSUPA) feature is also in the process of being standardised.This uplink packet access feature will adopt many of the features ofHSDPA.

In accordance with the 3GPP specifications, the HSDPA service may beused in both Frequency Division Duplex (FDD) mode and Time DivisionDuplex (TDD) mode.

In HSDPA, transmission code resources are shared amongst users accordingto their traffic needs. The base station or ‘Node-B’ is responsible forallocating and distributing the resources to the users, within aso-called scheduling task. Hence, for HSDPA, some scheduling isperformed by the RNC, whereas other scheduling may be performed by thebase station. Specifically, the RNC allocates a set of resources to eachbase station, which the base station can use exclusively for high-speedpacket services. The RNC furthermore controls the flow of data to andfrom the base stations.

Therefore, most packet-based systems contain schedulers that controlwhen the individual data packets are transmitted, in order to share theavailable resource, whether time-slots in a time division multipleaccess (TDMA) communication system or power and codes in a code divisionmultiple access (CDMA) communication system. An introduction toschedulers can be found in ‘Service discipline for guaranteedperformance service in packet-switching networks’, authored by HuiZhang, and published in the Proceedings of the IEEE, volume 83, no. 10,October 1995.

Referring now to FIG. 1, an example of UL data transfer 100, in a‘request and allocate’ system, is illustrated. The data transfer isperformed between a UE 105 and a network 110. The key attribute forschedulers operating in such systems is that the allocation of theshared resources in the uplink is based on a ‘request and allocate’principle. Specifically, when the UE 105 determines that it has new dataarriving in its buffers to be transmitted, in step 115, the UE 105transmits a request message 120 for resources from the network in aspecific message. This specific message usually contains an indicationof the volume of data in the UE's buffers that is to be transmitted.When the network receives this message in step 125, the request is thenpassed to the scheduler and subsequently uplink (UL) resources areallocated to the UE, in step 130. This allocation is signalled in aseparate allocation message, as shown in step 135. When the UE receivesthis message in step 140, the UE may send the UL data on the specifiedair interface resource(s), and the consequent data transfer is shown instep 145.

A similar, though simpler, procedure occurs in the downlink (DL)direction. Of course no message needs to be sent over the air interfaceto tell the scheduler the state of the DL buffers at the network end ofthe system. This means that allocation in the DL is subject to muchlower latency than in the UL.

Transport communication protocol (TCP) is a protocol in the well-knownTCP/IP (Internet Protocol) suite of communication protocols (see [RFC793] for a full description of the TCP protocol). TCP provides aconnection-orientated, reliable, byte stream service. The reliability ismaintained by the use of acknowledgement messages (ACKs) that are sentby the receiver back to the transmitter, in response to a receivedsegment. In this manner, lost or corrupted data segments may beindicated to the transmitter, and these lost or corrupted data segmentsmay be re-sent.

However, in TCP the receiver does not immediately send an acknowledgmentfor every received segment. A functionality termed ‘delayed ACK’ isemployed (see [RFC 813]). When a data segment is received, a delay timeris started and an ACK data segment is sent in response to one of thefollowing conditions:

-   -   a) The delay timer expires.    -   b) New Data is returned to the original transmitter of the        segment (i.e. in interactive style applications, such as        ‘rlogin’) and this new data can be ‘piggybacked’ with an ACK        message.    -   c) More segments are received from the transmitter.

In the case of bulk data transfer it is condition-(c) that is the mostlikely, as the transmitter is, ideally, continuously sending newsegments.

Typically only one more segment is required for an ACK to be sent. Thefollowing quote is from [RFC 1122]:

-   -   ‘When used, a TCP receiver MUST NOT excessively delay        acknowledgments. Specifically, an ACK SHOULD be generated for at        least every second full-sized segment, and MUST be generated        within 500 msec. of the arrival of the first unacknowledged        packet.’

Most current TCP stacks implement the delayed ACK functionality so thatan ACK is generated when a single TCP segment is received, whilst thedelay timer is running (i.e. an ‘ACK’ is transmitted for ‘every secondfull-sized data segment’ received, since the reception of a single TCPsegment is enough to start the timer in the first place). Also the delaytimer is typically set to 200 msec.

The delayed ACK feature is shown diagrammatically in FIG. 2, with a TCPsegment 215 transmitted between a transmitter 210 and a receiver 205(note that the typical configuration in wireless systems will be thatthe network is the transmitter and the UE is the receiver) Here, the TCPsegment 215 is received at the receiver 205. However, the receiver 205does not transmit an ACK message immediately, and waits until the delaytimer has expired, as no data arrives that can be piggy-backed onto thedata that is to be sent to the transmitter 210 in addition to no othersubsequent TCP segments are received from the transmitter 210. After thedelay timer expires, after a period 225, the receiver 205 transmits astand-alone ACK segment 230.

Thereafter, in the second case, two full-sized TCP segments 235 aretransmit by the transmitter 210. The two full-sized TCP segments 235 arereceived at the receiver 205. The receiver 205 does not immediatelytransmit an ACK to the transmitter 210, after receipt of the first ofthe two full-sized TCP segments 235. However, after receipt of thesecond of the two full-sized TCP segments 235, the receiver 205immediately transmits an ACK in step 240. For completeness, it isnoteworthy that FIG. 2 shows a typical case of ‘slow start’ in TCP.

In the case of bulk TCP data transfer the delayed ACK feature leads toan ACK being transmitted every other segment.

When TCP is used (for bulk data transfer) in ‘request and allocate’wireless communication systems (i.e. one using the shared channelconcept), a message flow between a UE 305 and the network 310 occurs,similar to the data flow illustrated in FIG. 3. Here, at least onefull-sized TCP segment arrives at a network's DL buffer, in step 315.The network 310 transmits a message to the UE 305 to allocate DLresources, as shown in step 320. This message is followed by the TCPdata transfer, as shown in step 325. The at least one full-sized TCPsegment is received by the UE 305, in step 330, which passes the atleast one full-sized TCP segment to its TCP memory stack.

The UE 305 then transmits a message to the network 310, requesting ULresources to transmit an ACK message, as shown in step 340. In responsethereto, the network 310 transmits a message to the UE 305 allocating ULresources, as shown in step 345. Thereafter, the UE 305 is able toimplement the data transfer in step 355, which includes an ‘ACK’message. Notably, a significant latency 350 exists with this request foran allocated resource.

Thus, there exists a need to provide an improved mechanism to providebulk IP data transfer flow.

SUMMARY OF THE INVENTION

In accordance with aspects of the present invention, there is providedapparatus, a wireless communication system, a method for acknowledgingan allocation of resource and a method for allocating resource andcomputer program product, as defined in the appended Claims.

Accordingly, in one embodiment of the present invention there isprovided an apparatus for use in allocating resource in a wirelesscommunication system employing transfer communication protocol (TCP)based data transfer between a network and a wireless subscribercommunication unit. The apparatus comprises a scheduler located in thenetwork, wherein the scheduler buffers a TCP data segment for downlink(DL) transmission. A transmitter arranged to transmit the buffered TCPdata segment to the UE; wherein the message indicates an allocation ofDL resources plus sufficient uplink resources to transfer a stand-aloneACK data segment.

The provision of a message that indicates an allocation of DL resourcesplus sufficient uplink resources to transfer a stand-alone ACK datasegment enables a wireless subscriber communication unit to process thedownlink message to identify an allocation of DL resources plussufficient uplink resources and transmit a stand-alone ACK data segmentin response to the downlink message.

In one embodiment of the present invention, the apparatus comprisescounting logic operably coupled to scheduler and arranged to count anumber of transmitted segments, as they are transferred to the UE.

The provision of counting logic provides a mechanism to count every DLfull sized segment separately in each TCP flow (if there are multiple)and use the counting logic to ensure that when the second segment issent UL resources are allocated. The counter is then reset.

In one embodiment of the present invention, the apparatus is located ina radio access network that comprises the scheduler arranged to allocateresources to a plurality of user equipment.

In one embodiment of the present invention, the apparatus is arranged tooperate in a 3^(rd) Generation Partnership Project (3GPP) cellularcommunication system.

In one embodiment of the present invention, the apparatus is arranged tooperate in a time division duplex code division multiple access cellularcommunication system.

In one embodiment of the present invention, a wireless subscribercommunication unit for use in acknowledging an allocation of resource ina wireless communication system employing transfer communicationprotocol (TCP) based data transfer between a network and the wirelesssubscriber communication unit comprises a receiver arranged to receive adownlink message comprising a TCP data segment. Processing logic,operably coupled to the receiver, is arranged to process the downlinkmessage to identify an allocation of DL resources plus sufficient uplinkresources to transfer a stand-alone ACK data segment. A transmitter isarranged to transmit a stand-alone ACK data segment in response to thedownlink message.

In one embodiment of the present invention, the wireless subscribercommunication unit immediately transmits the stand-alone ACK datasegment in the allocated UL resources following processing the downlinkmessage.

In one embodiment of the present invention, a method for allocatingresource in a wireless communication system employing transfercommunication protocol (TCP) based data transfer between a network and awireless subscriber communication unit comprises buffering a TCP datasegment for downlink (DL) transmission; transmitting the buffered TCPdata segment to the wireless subscriber communication unit within amessage. The message indicates an allocation of DL resources plussufficient uplink resources to transfer a stand-alone ACK data segmentfrom the wireless subscriber communication unit.

In one embodiment of the present invention, a method for acknowledgingan allocation of resource in a wireless communication system employingtransfer communication protocol (TCP) based data transfer between anetwork and a wireless subscriber communication unit comprises receivinga downlink message comprising a TCP data segment. The method furthercomprises processing the downlink message; identifying an allocation ofdownlink resources plus sufficient uplink resources to transfer astand-alone acknowledgement (ACK) data segment; and transmitting thestand-alone ACK data segment in response to the downlink message.

In one embodiment of the present invention, a computer program productcomprises executable program code for allocating resource in a wirelesscommunication system. The computer program product comprises programcode for buffering a TCP data segment for downlink (DL) transmission;transmitting the buffered TCP data segment to the wireless subscribercommunication unit within a message. The message indicates an allocationof DL resources plus sufficient uplink resources to transfer astand-alone ACK data segment from the wireless subscriber communicationunit.

In one embodiment of the present invention, there is provided wirelesscommunication system comprising a radio access network facilitatingcommunication to a plurality of wireless communication units. Thewireless communication system comprises a scheduler located in thenetwork, wherein the scheduler buffers a TCP data segment for downlink(DL) transmission; a transmitter arranged to transmit the buffered TCPdata segment to the UE. The message indicates an allocation of DLresources plus sufficient uplink resources to transfer a stand-alone ACKdata segment.

In one embodiment of the present invention, the wireless communicationsystem further comprises a wireless subscriber communication unitcomprising a receiver arranged to receive the downlink messagecomprising a TCP data segment; processing logic, operably coupled to thereceiver and arranged to process the downlink message to identify anallocation of downlink resources plus sufficient uplink resources totransfer a stand-alone ACK data segment; and a transmitter arranged totransmit a stand-alone ACK data segment in response to the downlinkmessage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a known example of UL data transfer, in a ‘requestand allocate’ system;

FIG. 2 illustrates a known delayed ‘ACK’ feature, with a TCP segmenttransmitted between a transmitter and a receiver; and

FIG. 3 illustrates a ‘request and allocate’ wireless communicationsystem where TCP is used for bulk data transfer in a message flowbetween a UE and a network. Embodiments of the invention will bedescribed, by way of example only, with reference to the accompanyingdrawings, in which:

FIG. 4 illustrates a 3GPP cellular communication system capable ofsupporting embodiments of the present invention; and

FIG. 5 illustrates a method to support a transmission of an ACK messagein a TCP-based wireless communication system employing resource andallocation acknowledge messages, according to embodiments of the presentinvention.

DESCRIPTION OF EMBODIMENTS OF THE INVENTION

In summary, embodiments of the present invention describe anarchitecture for supporting a scheduler within the Radio Access Networkis configured to allocate ‘ACK’ resources to a UE.

Referring first to FIG. 4, a typical, standard UMTS Radio Access Network(UTRAN) system 400 is conveniently considered as comprising:terminal/user equipment domain 410; a UMTS Terrestrial Radio AccessNetwork domain 420; and an infrastructure domain 430.

In the terminal/user equipment domain 410, terminal equipment (TE) 412is connected to mobile equipment (ME) 414 via the wired or wireless Rinterface. The ME 414 is also connected to a user service identitymodule (USIM) 416; the ME 414 and the USIM 416 together are consideredas user equipment (UE) 418. The UE may be for example a remote unit, amobile station, a communication terminal, a personal digital assistant,a laptop computer, an embedded communication processor or anycommunication element communicating over the air interface of thecellular communication system.

The UE 418 communicates data with a Node-B (base station) 422 in theradio access network domain 420 via the wireless Uu interface. Withinthe radio access network domain 420, the Node-B 422 communicates with aradio network controller (RNC) 424 via the Iub interface. The RNC 424communicates with other RNCs (not shown) via the Iur interface.

The Node-B 422 and the RNC 424 together form the UTRAN 426. The RNC 424communicates with a serving GPRS service node (SGSN) 432 in the corenetwork domain 430 via the Iu interface. Within the core network domain430, the SGSN 432 communicates with a gateway GPRS support node 434 viathe Gn interface; the SGSN 432 and the GGSN 434 communicate with a homelocation register (HLR) server 436 via the Gr interface and the Gcinterface respectively. The GGSN 434 communicates with public datanetwork 438 via the Gi interface.

Thus, the elements RNC 424, SGSN 432 and GGSN 434 are conventionallyprovided as discrete and separate units (on their own respectivesoftware/hardware platforms) divided across the radio access networkdomain 420 and the core network domain 430, as shown FIG. 4.

The RNC 424 is the UTRAN element responsible for the control andallocation of resources for numerous Node-Bs 422; typically 50 to 100Node-Bs may be controlled by one RNC. The RNC also provides reliabledelivery of user traffic over the air interfaces. RNCs communicate witheach other (via the Iur interface).

The SGSN 432 is the UMTS Core Network element responsible for SessionControl and interface to the HLR. The SGSN keeps track of the locationof an individual UE and performs security functions and access control.The SGSN is a large centralised controller for many RNCs.

The GGSN 434 is the UMTS Core Network element responsible forconcentrating and tunnelling user data within the core packet network tothe ultimate destination (e.g., internet service provider—ISP). Terminalequipment (TE) 412 is connected to mobile equipment (ME) 414 via thewired or wireless R interface. The ME 414 is also connected to a userservice identity module (USIM) 416; the ME 414 and the USIM 416 togetherare considered as user equipment (UE) 418. The UE 418 communicates datawith a Node-B (base station) 422 in the radio access network domain 420via the wireless Uu interface. Within the radio access network domain420, the Node-B 422 communicates with a radio network controller (RNC)424 via the Iub interface. The RNC 424 communicates with other RNCs (notshown) via the Iur interface. The Node-B 422 and the RNC 424 togetherform the UTRAN 426. The RNC 424 communicates with a serving GPRS servicenode (SGSN) 432 in the core network domain 430 via the Iu interface.Within the core network domain 430, the SGSN 432 communicates with agateway GPRS support node 434 via the Gn interface; the SGSN 432 and theGGSN 434 communicate with a home location register (HLR) server 436 viathe Gr interface and the Gc interface respectively. The GGSN 434communicates with public data network 430D via the Gi interface.

Thus, the elements RNC 424, SGSN 432 and GGSN 434 are conventionallyprovided as discrete and separate units (on their own respectivesoftware/hardware platforms) divided across the radio access networkdomain 420 and the core network domain 430, as shown FIG. 4.

The RNC 424 is the UTRAN element responsible for the control andallocation of resources for numerous Node-B's 422; typically 50 to 400Node-B's may be controlled by one RNC. The RNC 424 also providesreliable delivery of user traffic over the air interfaces. RNCscommunicate with each other (via the Iur interface).

The SGSN 432 is the UMTS Core Network element responsible for SessionControl and interface to the HLR. The SGSN keeps track of the locationof an individual UE and performs security functions and access control.The SGSN is a large centralised controller for many RNCs.

The GGSN 434 is the UMTS Core Network element responsible forconcentrating and tunnelling user data within the core packet network tothe ultimate destination (e.g., internet service provider—ISP).

Such a UTRAN system and its operation are described more fully in the3rd Generation Partnership Project technical specification documents3GPP TS 25.401, 3GPP TS 23.060, and related documents, available fromthe 3GPP website at www.3gpp.org, and need not be described herein inmore detail.

Within the RNC 424, separate functional blocks exist that have beenincorporated or adapted in accordance with embodiments of the presentinvention. In particular, as shown in FIG. 4, a scheduler 428,comprising or operably coupled to counting logic 429, has been adaptedto perform the inventive concept as described further with respect toFIG. 5.

Referring now to FIG. 5, a data flow process 500 is illustrated betweena UE 505 and a scheduler 428 in the network 510. The inventive conceptdescribed in FIG. 5 commences with a full-sized TCP data segmentarriving at a DL buffer within the network 510. The network determinesthat an ACK is likely to be generated by the receiving UE in response tothe transmitted TCP data segment, in step 515. The knowledge is based onthe fact that with a delayed ACK feature there will be an ACK everyother segment. It is therefore possible to easily count DL segments (foreach TCP flow, if necessary) and then when the counter reaches twoallocate UL resources accordingly. The counter is then reset. Thus, thescheduler is made aware that the data being transferred is using the TCPprotocol following transmission of a message to the UE, as shown in step525.

Notably, the scheduler arranges for the message to indicate anallocation of DL resources plus sufficient UL resources to transfer astand-alone ACK data segment 530, in step 520. The scheduler 428 (fromFIG. 4) continues allocating DL resources to transfer the segments tothe UE 505. Notably, the scheduler comprises counting logic 429 arrangedto count a number of transmitted segments, as they are transferred tothe UE 505. In this manner, the scheduler 428 is made aware of when theend of each data segment is likely to be fully transferred to the UE505.

In accordance with one embodiment of the present invention, thefull-sized TCP data segment is received by the UE 505 and passed to theTCP memory stack of the UE 505. The UE then responds with a stand-aloneACK data segment 545, in step 535. In accordance with one embodiment ofthe present invention, the stand-alone ‘ACK’ data segment may beimmediately placed in allocated UL resources, so there is no requirementto transmit a message to request UL resources, in step 550.

In one embodiment of the present invention, at the end of every secondsegment, or greater number of segments depending upon the particular TCPimplementation, the allocation message containing a downlink resourceallocation will also contain enough uplink resource allocation for astand-alone ACK to be transmitted. A stand-alone ACK is typically ‘40’to ‘60’ bytes (though this might be less if some form of headercompression is applied). Hence, in this embodiment of the presentinvention, the UL resource is provided with enough bytes to include thestand-alone ACK message. It is also envisaged that the start of the ULallocation may also be slightly delayed in time, from the DLtransmission, in order for the TCP stack at the UE to process thedownlink segments and generate the stand-alone ACK.

It is envisaged that it may not be possible to exactly predict a sendingof an ACK from the UE. For example, a missing segment may be detectedand an ACK generated unexpectedly. Similarly, there may be piggybackeddata to send and the allocation may be too small to carry the ACK plusdata segment. However, it has been determined that the overallstatistical performance is to significantly improve latency at the costof some wasted uplink resource.

In summary, the inventive concept of the present invention aims toprovide at least one or more of the following features:

-   -   (i) A method and apparatus to provide reduced latency in TCP;    -   (ii) In large bulk data transfer cases, such as file transfer        protocol (FTP), the reduced latency may lead to improved        throughput, due to the fact that the overall throughput may be        limited by the window size (i.e. number of unacknowledged        segments) rather than the throughput possible across the air        interface; and    -   (iii) In short data transfers such, as hyper-text transfer        protocol (HTTP), the observed throughput may be significantly        affected by the latency, due to slow start functionality of TCP.        Since the latency will be reduced using the inventive concept        herein described the overall observed performance (for page        download time in the case of HTTP) is improved.

In particular, it is envisaged that the aforementioned inventive conceptmay be applied by a semiconductor manufacturer to any signal processingintegrated circuit (IC). It is further envisaged that, for example, asemiconductor manufacturer may employ the inventive concept in a designof a stand-alone device, or application-specific integrated circuit(ASIC) and/or any other sub-system element.

It will be appreciated that any suitable distribution of functionalitybetween different functional units or logic elements may be used withoutdetracting from the inventive concept herein described. Hence,references to specific functional devices or elements are only to beseen as references to suitable means for providing the describedfunctionality, rather than indicative of a strict logical or physicalstructure or organization.

Aspects of the invention may be implemented in any suitable formincluding hardware, software, firmware or any combination of these. Theelements and components of an embodiment of the invention may bephysically, functionally and logically implemented in any suitable way.Indeed, the functionality may be implemented in a single unit or IC, ina plurality of units or ICs or as part of other functional units.

Although the present invention has been described in connection withsome embodiments, it is not intended to be limited to the specific formset forth herein. Rather, the scope of the present invention is limitedonly by the accompanying claims. Additionally, although a feature mayappear to be described in connection with particular embodiments, oneskilled in the art would recognize that various features of thedescribed embodiments may be combined in accordance with the invention.In the claims, the term ‘comprising’ does not exclude the presence ofother elements or steps.

Furthermore, although individual features may be included in differentclaims, these may possibly be advantageously combined, and the inclusionin different claims does not imply that a combination of features is notfeasible and/or advantageous. Also, the inclusion of a feature in onecategory of claims does not imply a limitation to this category, butrather indicates that the feature is equally applicable to other claimcategories, as appropriate.

Furthermore, the order of features in the claims does not imply anyspecific order in which the features must be performed and in particularthe order of individual steps in a method claim does not imply that thesteps must be performed in this order. Rather, the steps may beperformed in any suitable order. In addition, singular references do notexclude a plurality. Thus, references to “a”, “an”, “first”, “second”etc. do not preclude a plurality.

Thus, an improved wireless communication system, apparatus, integratedcircuit, and a method of operation therefor have been described, whereinthe aforementioned disadvantages with prior art arrangements have beensubstantially alleviated.

1. Apparatus for use in allocating resource in a wireless communicationsystem employing transfer communication protocol (TCP) based datatransfer between a network and a wireless subscriber communication unit,the apparatus comprising: a scheduler located in the network, whereinthe scheduler buffers a TCP data segment for downlink (DL) transmissionto user equipment (UE); counting logic operably coupled to the schedulerand arranged to count a number of data segments transmitted to the UE,wherein the scheduler is arranged to allocate uplink (UL) resources forsupporting a transmission of a stand-alone acknowledgement (ACK) datasegment from the UE in response to the counting logic counting apredetermined number of data segments; and a transmitter arranged totransmit to the user equipment (UE) an allocation message that indicatesan allocation of DL resources and then to transmit to the user equipmentthe buffered TCP data segment on the allocated DL resources, whereinwhen the counting logic has counted the predetermined number of datasegments the allocation message indicates an allocation of uplinkresources sufficient to transfer the stand-alone ACK data segment. 2.The apparatus of claim 1 wherein the apparatus is located in a radioaccess network that comprises the scheduler arranged to allocateresources to a plurality of UEs.
 3. The apparatus of claim 1 wherein theapparatus is a communication unit arranged to operate in a 3rdGeneration Partnership Project (3GPP) cellular communication system. 4.The apparatus of claim 1 wherein the apparatus is arranged to operate ina time division duplex code division multiple access cellularcommunication system.
 5. A wireless subscriber communication unit foruse in acknowledging an allocation of resource in a wirelesscommunication system employing transfer communication protocol (TCP)based data transfer between a network and the wireless subscribercommunication unit, the wireless subscriber communication unitcomprising: a receiver arranged to receive an allocation message and aTCP data segment; processing logic, operably coupled to the receiver andarranged to process the allocation message to identify an allocation ofDL resources to receive the TCP data segment plus sufficient uplink (UL)resources to transfer a stand-alone acknowledgement (ACK) data segment,where the allocation of UL resources to support transmission of thestand-alone ACK data segment is based on a count performed in thenetwork of a predetermined number of data segments transmitted to thewireless subscriber communication unit; and a transmitter arranged totransmit the stand-alone ACK data segment in response to the message. 6.The wireless subscriber communication unit of claim 5 wherein thewireless subscriber communication unit immediately transmits thestand-alone ACK data segment in the allocated UL resources followingprocessing the downlink message.
 7. The wireless subscribercommunication unit of claim 5 wherein the wireless subscribercommunication unit is arranged to operate in a 3rd GenerationPartnership Project (3GPP) cellular communication system.
 8. Thewireless subscriber communication unit of claim 5 wherein the wirelesssubscriber communication unit is arranged to operate in a time divisionduplex code division multiple access cellular communication system.
 9. Amethod for allocating resource in a wireless communication systememploying transfer communication protocol (TCP) based data transferbetween a network and a wireless subscriber communication unit, themethod comprising: buffering a TCP data segment for downlink (DL)transmission to the wireless subscriber communication unit; and countinga number of data segments transmitted to the wireless subscribercommunication unit; allocating uplink (UL) resources for supporting atransmission of a stand-alone acknowledgement (ACK) data segment fromthe wireless subscriber communication unit in response to the countingstep having counted at least a predetermined number of the datasegments; and first transmitting to the wireless subscribercommunication unit an allocation message wherein the message indicatesan allocation of DL resources, and then transmitting to the wirelesssubscriber communication unit the buffered TCP data segment on theallocated DL resources, wherein when the count of the data segments atleast equals the predetermined number of the data segments theallocation message indicates an allocation of UL resources sufficient totransfer the stand-alone ACK data segment.
 10. The method for allocatingresource of claim 9 wherein the method is applied in a 3rd GenerationPartnership Project (3GPP) cellular communication system.
 11. The methodfor allocating resource of claim 9 wherein the method is applied in atime division duplex code division multiple access cellularcommunication system.
 12. A method for acknowledging an allocation ofresource in a wireless communication system employing transfercommunication protocol (TCP) based data transfer between a network and awireless subscriber communication unit, the method comprising: receivingan allocation message and a TCP data segment; processing the allocationmessage; identifying an allocation of DL resources to receive the TCPdata segment plus sufficient uplink (UL) resources to transfer astand-alone acknowledgement (ACK) data segment, where the allocation ofUL resources to support transmission of the stand-alone ACK data segmentis based on a count performed in the network of a predetermined numberof data segments transmitted to the wireless subscriber communicationunit; and transmitting the stand-alone ACK data segment in response tothe allocation message.
 13. The method for acknowledging an allocationof resource claim 12 wherein the step of transmitting the stand-aloneACK data segment in the allocated UL resources is performed immediatelyfollowing the step of processing and identifying.
 14. The method foracknowledging an allocation of resource of claim 12 wherein the methodis applied in a 3rd Generation Partnership Project (3GPP) cellularcommunication system.
 15. The method for acknowledging an allocation ofresource of claim 12 wherein the method is applied in a time divisionduplex code division multiple access cellular communication system. 16.A non-transitory computer program product having executable program codestored therein for allocating resource in a wireless communicationsystem, the program code operable for when executed at a communicationunit: buffering a TCP data segment for downlink (DL) transmission to awireless subscriber communication unit; and counting a number of datasegments transmitted to the wireless subscriber communication unit;allocating uplink (UL) resources for supporting a transmission of astand-alone acknowledgement (ACK) data segment from the wirelesssubscriber communication unit in response to when the count of the datasegments at least equals a predetermined number of the data segments;and first transmitting to the wireless subscriber communication unit anallocation message that indicates an allocation of DL resources and thentransmitting to the wireless subscriber communication unit the bufferedTCP data segment on the allocated DL resources, wherein when the countof the data segments at least equals the predetermined number of thedata segments the allocation message indicates an allocation of ULresources sufficient to transfer the stand-alone ACK data segment.
 17. Awireless communication system comprising a radio access networkfacilitating communication to a plurality of wireless subscribercommunication units, the wireless communication system comprising: ascheduler located in the network, wherein the scheduler buffers atransfer communication protocol (TCP) data segment for downlink (DL)transmission to a wireless subscriber communication unit; and countinglogic operably coupled to the scheduler and arranged to count a numberof data segments transmitted to the UE, wherein the scheduler isarranged to allocate uplink (UL) resources for supporting a transmissionof a stand-alone acknowledgement (ACK) data segment from the UE inresponse to the counting logic counting a predetermined number of datasegments; and a transmitter arranged to transmit to the wirelesssubscriber communication unit an allocation message that indicates anallocation of DL resources and then to transmit to the wirelesssubscriber communication unit the buffered TCP data segment on theallocated DL resources, wherein when the counting logic has counted thepredetermined number of data segments the allocation message indicatesan allocation of uplink (UL) resources sufficient to transfer thestand-alone ACK data segment.
 18. The wireless communication system ofclaim 17 wherein the wireless subscriber communication unit comprises: areceiver arranged to receive the DL allocation message comprising andthe transfer communication protocol (TCP) data segment; processinglogic, operably coupled to the receiver and arranged to process theallocation message to identify an allocation of DL resources to receivethe TCP data segment plus sufficient uplink resources to transfer thestand-alone acknowledgement (ACK) data segment; and a transmitterarranged to transmit the stand-alone ACK data segment in response to theallocation message.
 19. The wireless communication system of claim 17wherein the wireless communication system is a 3rd GenerationPartnership Project (3GPP) cellular communication system.
 20. Thewireless communication system of claim 17 wherein the wirelesscommunication system is a time division duplex code division multipleaccess cellular communication system.
 21. An apparatus, comprising: amemory; a processor coupled to the memory; and program code stored inthe memory and executable on the processor, the program code operablefor: buffering a transfer communication protocol (TCP) data segment fordownlink (DL) transmission to a wireless subscriber communication unit;counting a number of data segments transmitted to the wirelesssubscriber communication unit; allocating uplink (UL) resources forsupporting a transmission of a stand-alone acknowledgement (ACK) datasegment from the wireless subscriber communication unit in response towhen the count of data segments equals a predetermined number of datasegments; and first transmitting to the wireless subscribercommunication unit an allocation message that indicates an allocation ofDL resources and then transmitting to the wireless subscribercommunication unit the buffered TCP data segment on the allocated DLresources, wherein when the count of data segments at least equals thepredetermined count of data segments the allocation message indicates anallocation of UL resources sufficient to transfer the stand-alone ACKdata segment.
 22. An apparatus, comprising: non-transitory logic forbuffering a transfer communication protocol (TCP) data segment fordownlink (DL) transmission to a wireless subscriber communication unit;and non-transitory logic for counting a number of data segmentstransmitted to the wireless subscriber communication unit;non-transitory logic for allocating uplink (UL) resources for supportinga transmission of a stand-alone acknowledgement (ACK) data segment fromthe wireless subscriber communication unit in response to when the countof the number of data segments at least equals a predetermined number ofdata segments; and non-transitory logic for transmitting to the wirelesssubscriber communication unit an allocation message that indicates anallocation of DL resources and for then transmitting to the wirelesssubscriber communication unit the buffered TCP data segment on theallocated DL resources, wherein when the count of the number of datasegments at least equals the predetermined number of data segments theallocation message indicates an allocation of UL resources sufficient totransfer the stand-alone ACK data segment.
 23. An apparatus, comprising:a memory; a processor coupled to the memory; and program code stored inthe memory and executable on the processor, the program code operablefor: receiving an allocation message and a transfer communicationprotocol (TCP) data segment; processing the allocation message;identifying an allocation of DL resources to receive the TCP datasegment plus sufficient uplink (UL) resources to transfer a stand-aloneacknowledgement (ACK) data segment, where the allocation of UL resourcesto support transmission of the stand-alone ACK data segment is based ona count performed external to the apparatus of a predetermined number ofdata segments transmitted to the wireless subscriber communication unit;and transmitting the stand-alone ACK data segment in response to theallocation message.
 24. An apparatus, comprising: non-transitory logicfor receiving allocation message and a transfer communication protocolTCP data segment; non-transitory logic for processing the allocationmessage; non-transitory logic for identifying an allocation of DLresources to receive the TCP data segmenet plus sufficient uplink (UL)resources to transfer a stand-alone acknowledgement (ACK) data segment,where the allocation of UL resources to support transmission of thestand-alone ACK data segment is based on a count performed external tothe apparatus of a predetermined number of data segments transmitted tothe wireless subscriber communication unit; and non-transitory logic fortransmitting the stand-alone ACK data segment in response to theallocation message.